In most Software engineering project, users are only involved in the beginning of the project as a help to design the requirements specification but users can be involved after this phase too, but is it effective to do so? With this report we would like to investigate how effective it is to involve users after the requirements specification has been written and approved. To find out how effective it is to involve the users we try some fast and simple involvement techniques on a quite far gone project. These techniques include ethnographic studies, prototypes and surveys. We also interviewed a couple of people who work with usability and finally delivered a report with our results to them to find out if they found our result relevant. By also documenting how much time we spent involving users we will show to which degree user involvement is effective. We found out that a couple of fast techniques could get very much result in the form of usability enhancing suggestions to the developers.

This report describes a final thesis done during the spring of 2008 as part of the bachelor degree in computer engineering degree at the School of Engineering in Jönköping.The client is working in the consulting business and is involved in, amongst others, work regarding information security. Within this field they perform so called Threat, Risk and Vulnerability assessments. Today these assessments are done by a predefined method, but many details are controlled by the person documenting the project. A wish was made that the implementation was standardized, it should also ease the task of estimating the need for time and money. The solution for this seems to be a software tool.

This paper describes the evolutionary development of an information system for a small company. The company performs overhaul of forklifts and cleaning machines. The company has already an information system that handles the reports from these overhauls but it needs a supplementary tool that assist the chief planner to plan forthcoming overhauls.It should be able to display coming overhauls in a timetable and eventually print them, either to a PDF file or to a document. The timetables this function produces will help the chief planner and the assemblers to get a good overview of their day-to-day work.The tool needs to be intelligent in that way that it takes into consideration were in the country different assignments will be performed. So that time consuming travels over great distances can be avoided.

There are several methods and models within the areas of Software engineering on how to proceed during a software development process. For each of these methods and models there are benefits and drawbacks, depending on how you choose to look at them. A difference of principle between the different models is that they either advocate iterative development or not. In parts of Software engineering one makes use of different methods depending on which is most fitting in a specific situation. There are several methods on how to recieve more qualitative data from the end-users during the requirement collection, but the reappearing pattern is still user centric participation, which means that the user participates more actively in part of or the entire development process.

Webbaserat Tidrapporteringsystem.

Open source software has recently been discussed, not least in media as a revolution in IT. A number of advantages have been listed in changing proprietary software into open source software. Examples of such pros are no expenses for license fees and improved efficiency. In spite of this, few users have made this change. One of the reasons is a distrust of the quality in open source software.

Open source software has recently been discussed, not least in media as a revolution in IT. A number of advantages have been listed in changing proprietary software into open source software. Examples of such pros are no expenses for license fees and improved efficiency. In spite of this, few users have made this change. One of the reasons is a distrust of the quality in open source software.

In most Software engineering project, users are only involved in the beginning of the project as a help to design the requirements specification but users can be involved after this phase too, but is it effective to do so? With this report we would like to investigate how effective it is to involve users after the requirements specification has been written and approved. To find out how effective it is to involve the users we try some fast and simple involvement techniques on a quite far gone project. These techniques include ethnographic studies, prototypes and surveys. We also interviewed a couple of people who work with usability and finally delivered a report with our results to them to find out if they found our result relevant.

Abstract The purpose of writing this thesis was to improve methods during requirements engineering phase. Usercentred system engineering has some problem areas, which are examined and verified to create a new guideline for developers. This guideline tends to make requirements engineering more effective and help developers create more concrete requirements. It is not uncommon that system development projects ends up with unsatisfied users or delay in deliveries. The reasons are different kinds of communication problems between users and developers during verification of requirements. There is a therapy model, called solution-focused therapy, used in family and individual therapy. The model focuses on solutions for the future instead of problems in the past.

The computer consultant company Create in Lund AB wishes to facilitate their invoice routines, as it at present is required that the administration finds and compares information from two different systems.The purpose of this thesis is to develop an invoice management system that simplifies the invoice management process for the administration at Create. During the development of the system, I have chosen to follow the software development process Unified Process and also tried to find design patterns that can be applied to the integration.The result of my project is a self-contained application developed using the Java programming language that communicates with the databases of the other two systems and presents relevant information to the user as a set of invoices. Of the 23 design patterns I studied, I used four of them in the invoice management system. However I couldn?t find any connection between any design pattern and the integration of systems.

This bachelor thesis portray a project where the main task were to develop a computer based system prototype for handling of absence report at the upper secondary school af Chapman in Karlskrona. The project has been conducted in cooperation with students from the university programs Software engineering and information economy at Blekinge Institute of Technology. Our task as MDA-students have been to survey the process of absence report of today through field studies and give a proposal of a graphical user interface which later were developed by the software engineers. The thesis also handles the cooperation with other students from other university programs..

This thesis has been carried out in New Zealand in collaboration with the University of Waikato. In association with Dr. Mike Duke the purpose of this work is to investigate whether two different software for modeling of photovoltaic systems are useful in the teaching of solar energy.The next ten years grid-connected photovoltaic systems are assumed to increase and therefore also a rising demand for people with engineering knowledge are to be predicted. For engineer students with a focus on solar energy a more practical teaching with design software´s can be a good method to make the students comprehend more when it comes to large scale photovoltaic systems and be more prepared for working life.The software´s used is called Transient System Simulation (TRNSYS) and Photovoltaic Systems (PVSYST) which are both well used throughout the world. To assess the reliability of the software´s, a reference solar power plant at 16.1 kWp installed capacity are used, which consists of photovoltaic modules from four different manufacturers.

This essay analyzes the market for entertainment software by identifying and explain the products typical properties, in addition i clarifies the behavior of consumers and producers. One of the most important property related to software is the ease with which it can be reproduced. When such reproduction is done illicit it´s called piracy. The software industry often claims that piracy leads to big losses for the companies as well as in welfare, the essay clarifies that this doesn´t has to be the case. On the contrary the possibility to cheap production and distribution may lead to an increased welfare.

Marknaden för mobila system har utvecklats enormt snabbt de senaste åren. Idag är det ett område med en allt större omsättning och det har vuxit fram som en helt ny gren inom Software engineering. Utvecklare av mobila applikationer står ständigt inför en utmaning när det gäller att välja vilket mobilt system man ska satsa på när man utvecklar applikationer. Valet av system kan vara helt avgörande för om man hittar rätt målgrupp av konsumenter och därmed kan generera tillräckligt med omsättning för att driva lönsam utveckling av applikationer. Det räcker inte att enbart kolla på vilket system som har mest användare eller vilket system som genererar mest omsättning, utan man bör noggrant överväga de förhållande som gäller för just den applikation som ska utvecklas. Genom att följa denna guiden och överväga de olika faktorer som vi har sammanställt så kan man som utvecklare göra ett val som är baserat på aktuella marknadsundersökningar.

Abstrakt Social Engineering är konsten att manipulera människor, för att på så sätt vinna deras förtroende. Med hjälp av detta förtroende kan attackeraren sedan kringgå säkerhetssystem och få tillgång till organisationers information. Vi har i denna uppsats genomfört elva intervjuer på tre stora organisationer med både IT-chefer och övrig personal. Med dessa intervjuer har vi sedan försökt få en bild av hur medvetenheten ser ut samt vilka åtgärder organisationerna tar för att förhindra Social Engineering. Med denna uppsats vill vi belysa den ovisshet som råder kring Social Engineering, men även farorna och hur effektiv en attack av denna typ kan vara.